Skip to content

Update MoonBit extension to v0.1.7#6649

Open
Metalymph wants to merge 2 commits into
zed-industries:mainfrom
Metalymph:update-moonbit-v0.1.6
Open

Update MoonBit extension to v0.1.7#6649
Metalymph wants to merge 2 commits into
zed-industries:mainfrom
Metalymph:update-moonbit-v0.1.6

Conversation

@Metalymph

@Metalymph Metalymph commented Jun 27, 2026

Copy link
Copy Markdown

Summary

This updates the existing MoonBit extension to v0.1.7.

Since the previous discussion, I have joined the existing quirk-lab/zed-moonbit repository as a maintainer, and the MoonBit 0.10 support has been merged there. This keeps MoonBit support consolidated into a single maintained extension.

Changes

  • Update MoonBit extension to v0.1.7
  • Update the extension submodule to the latest release commit
  • Keep the extension pointing to quirk-lab/zed-moonbit
  • Includes MoonBit 0.10 grammar and syntax support
  • Restores automatic MoonBit language server installation
  • Restores MoonBit workspace configuration forwarding
  • Restores the moonbit language server ID for compatibility with existing Zed settings

This PR updates the existing extension only; it does not introduce a second MoonBit extension.

Validation

  • git diff --check
  • Verified .gitmodules points to https://github.com/quirk-lab/zed-moonbit.git
  • Verified [moonbit].version = "0.1.7" in extensions.toml
  • Verified extensions/moonbit points to tag v0.1.7 commit 4d2e9cb40c16adbfa4c16f6c5fabc1c975e3419a
  • Verified tracked diff is limited to extensions.toml and extensions/moonbit
  • In quirk-lab/zed-moonbit: cargo fmt --check, cargo check, just validate-queries, just test-syntax

pnpm build could not complete locally due to an unrelated existing TypeScript environment issue: TS2688: Cannot find type definition file for 'minimatch'. The MoonBit update diff is limited to the extension version and submodule pointer.

@cla-bot cla-bot Bot added the cla-signed label Jun 27, 2026
@MrSubidubi MrSubidubi changed the title Update MoonBit extension to v0.1.6 Update MoonBit to v0.1.6 Jun 27, 2026

@MrSubidubi MrSubidubi left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You lost some capabilites such as the auto-language server install as well as the workspace configuration and the renaming of the language server ID is a somewhat breaking change. Were both intentional?

@Metalymph

Copy link
Copy Markdown
Author

Good catch, thanks!

Neither was intended as a regression.

When syncing the repositories I treated my implementation as the source of truth and focused primarily on bringing the extension up to date with the MoonBit 0.10 grammar, validation pipeline, and CI. In doing so I unintentionally dropped those existing capabilities.

I’ll restore the auto-install behavior, preserve the existing language server ID for backwards compatibility, and keep the remaining improvements from the synchronization.

@Metalymph Metalymph changed the title Update MoonBit to v0.1.6 Update MoonBit extension to v0.1.7 Jun 27, 2026
@Metalymph

Copy link
Copy Markdown
Author

Good catch — thanks.

Those regressions were not intentional. I’ve patched the extension and updated this PR to v0.1.7.

Changes made:

  • restored auto-install for @moonbit/moonbit-lsp
  • restored workspace configuration forwarding
  • restored language server ID compatibility by using [language_servers.moonbit]
  • kept the MoonBit 0.10 grammar/query updates intact

The registry PR now points to quirk-lab/zed-moonbit tag v0.1.7.

Validation passed:

  • extension repo: cargo fmt --check, cargo check, just validate-queries, just test-syntax
  • registry repo: git diff --check
  • verified .gitmodules still points to https://github.com/quirk-lab/zed-moonbit.git
  • verified registry diff is limited to extensions.toml and the extensions/moonbit submodule pointer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants